Ownership selection in VPC tiers and VPC public IPs#9692
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #9692 +/- ##
=========================================
Coverage 18.09% 18.09%
- Complexity 16723 16725 +2
=========================================
Files 6037 6037
Lines 542580 542671 +91
Branches 66427 66451 +24
=========================================
+ Hits 98155 98179 +24
- Misses 433399 433465 +66
- Partials 11026 11027 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@blueorangutan package |
|
@sureshanaparti a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 11164 |
|
This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch. |
|
@gpordeus could you fix the conflicts? |
|
@gpordeus Since this is for the 4.22.1 release, could you retarget the PR to the 4.22 branch? |
Co-authored-by: Fabricio Duarte <fabricio.duarte.jr@gmail.com>
68a3bfe to
369984b
Compare
|
Hi, @rajujith, @sureshanaparti, @JoaoJandre and @winterhazel Sorry for taking so long on getting back to this, it had been a while since I made this and the conflicts with 4.22 threw me for a loop. I fixed the conflicts with the main branch and I fixed the instance listing when the tier belongs to a project. Could you take another look? |
|
@blueorangutan package |
|
@sureshanaparti a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 17914 |
Description
This PR adds the "ownership selection" UI fields to VPC tiers and VPC public IPs.
The "vpcAccess" response attribute was added so the UI can know if the caller has access to the VPC without needing to make a whole new request. This is needed to avoid 404 links (since router.resolve is assembled through API permissions) and so the UI can present the correct public IPs to their possible network tiers (e.g. if the User has tiers of two different VPCs, they can't use one's public IP in the other).
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
New tier possible owners' listing
Tier listing
User accessing their tier of the Admin's VPC
Possible owners for new IP
How Has This Been Tested?
Environment with domains Root (with accounts Root Admin and User), Root/1 (with a Domain Admin), Root/A (with a Domain Admin) and Root/A/B (with a Domain Admin and a User). There is a Project in each domain, owned by the respective admins.
How did you try to break this feature and the system with this change?